Skip to content

Comments

Replace assert_empty with assert_equal using explicit literals#237

Open
koic wants to merge 1 commit intomodelcontextprotocol:mainfrom
koic:replace_assert_empty_with_assert_equal_using_explicit_literals
Open

Replace assert_empty with assert_equal using explicit literals#237
koic wants to merge 1 commit intomodelcontextprotocol:mainfrom
koic:replace_assert_empty_with_assert_equal_using_explicit_literals

Conversation

@koic
Copy link
Member

@koic koic commented Feb 24, 2026

Motivation and Context

Due to overly aggressive detection by RuboCop Minitest, the distinction between [] and {} was uniformly replaced with assert_empty, making it impossible to differentiate between them. As a result of rubocop/rubocop-minitest#344, where the Minitest/AssertEmptyLiteral cop was disabled, the return value has been expressed using explicit literal forms.

How Has This Been Tested?

Existing tests pass.

Breaking Changes

None.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update

Checklist

  • I have read the MCP Documentation
  • My code follows the repository's style guidelines
  • New and existing tests pass locally
  • I have added appropriate error handling
  • I have added or updated documentation as needed

Due to overly aggressive detection by RuboCop Minitest, the distinction between `[]` and `{}` was uniformly replaced with `assert_empty`,
making it impossible to differentiate between them.
As a result of rubocop/rubocop-minitest#344, where the `Minitest/AssertEmptyLiteral` cop was disabled,
the return value has been expressed using explicit literal forms.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant